A few suggestions below...

Looking at the logs, I don't know how common is the following scenario: same individual, repeated same event on the same dat i.e. you would get a number of entries that were potentially of a different execution of the same event. If so, you could add an incrementing counter that gets logged as an identifier to group the entries in the EAV table. Might not be necessary if this doesn't happen.

Thanks @tamuri, I have now included a sim-wide counter of events being ran that is appended as a unique identifier to the event name when logged (this doesn't apply to birth events, which I think we can safely assume only occur once per individual!)

I have additionally included a similar counter - which in this case is however reset for each event - which tracks the instance of consumable requests within that HSI, ensuring that if multiple consumable calls occur within the same HSI_Event these can be logged separately.

I have now included a sim-wide counter of events being ran that is appended as a unique identifier to the event name when logged

Looks good, though better to put the identifier as a new, separate, column in the row, which would allow the use of the event name for any purpose.

Some checks failing